-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2913: Update domain request screenreader outputs [ES] #3193
base: main
Are you sure you want to change the base?
Conversation
@@ -27,6 +27,10 @@ h2 { | |||
.usa-form, | |||
.usa-form fieldset { | |||
font-size: 1rem; | |||
legend em { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that our field headings and subheadings are included as legend items in the screenreader fix, we're setting font-size to 1rem to preserve their font size 16px.
… es/2913-domain-request-screenreader
@@ -149,6 +149,11 @@ footer { | |||
color: color('primary'); | |||
} | |||
|
|||
.usa-radio { | |||
margin-top: 1rem; | |||
font-size: 1.06rem; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added to preserve styling of our radio buttons (bigger text, margins)
@@ -34,6 +34,9 @@ h2 { | |||
.usa-form, | |||
.usa-form fieldset { | |||
font-size: 1rem; | |||
.usa-legend { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that our field headings and subheadings are moved to the legends in the screenreader fix, we're updating the font size of our legends to maintain our font size of 16px (originally 16.96px from usa-legend font size default being 1.06rem)
@@ -2,15 +2,25 @@ | |||
class="{% if label_classes %} {{ label_classes }}{% endif %}{% if label_tag == 'legend' %} {{ legend_classes }}{% endif %}" | |||
{% if not field.use_fieldset %}for="{{ widget.attrs.id }}"{% endif %} | |||
> | |||
{% if span_for_text %} | |||
<span>{{ field.label }}</span> | |||
{% if legend_heading %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Integrates legends into our labels so that their contents are tied to screenreader output
🥳 Successfully deployed to developer sandbox es. |
2 similar comments
🥳 Successfully deployed to developer sandbox es. |
🥳 Successfully deployed to developer sandbox es. |
Scope question - do we want expand these screenreader outputs to the portfolio forms as well? I can change them wherever applicable but feel free to let me know if we want this only scoped to our non org model domain request form |
|
||
{% with add_class="usa-radio__input--tile" add_legend_class="usa-sr-only" %} | ||
<div class="margin-top-2"> | ||
{% with add_class="usa-radio__input--tile" add_legend_heading="Are there other employees who can help verify your request?" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
widget=forms.Textarea(), | ||
widget=forms.Textarea( | ||
attrs={ | ||
"aria-label": "You don’t need to provide names of other employees now, \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<!-- Toggle --> | ||
<em>Select one. <abbr class="usa-hint usa-hint--required" title="required">*</abbr></em> | ||
{% with add_class="usa-radio__input--tile" add_legend_class="usa-sr-only" %} | ||
{% with add_class="usa-radio__input--tile" add_legend_class="margin-top-0" add_legend_heading="Are you working with a CISA regional representative on your domain request?" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{% if legend_heading %} | ||
<h2 class="{{ legend_classes }}">{{ legend_heading }} </h2> | ||
{% if widget.attrs.id == 'id_additional_details-has_cisa_representative' %} | ||
<p>.gov is managed by the Cybersecurity and Infrastructure Security Agency. CISA has <a href="https://www.cisa.gov/about/regions" target="_blank">10 regions</a> that some organizations choose to work with. Regional representatives use titles like protective security advisors, cyber security advisors, or election security advisors.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<!-- Toggle --> | ||
<em>Select one. <abbr class="usa-hint usa-hint--required" title="required">*</abbr></em> | ||
{% with add_class="usa-radio__input--tile" add_legend_class="usa-sr-only" %} | ||
{% with add_class="usa-radio__input--tile" add_legend_heading="Is there anything else you’d like us to know about your domain request?" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, thanks Erin!
🥳 Successfully deployed to developer sandbox es. |
1 similar comment
🥳 Successfully deployed to developer sandbox es. |
🥳 Successfully deployed to developer sandbox es. |
🥳 Successfully deployed to developer sandbox es. |
🥳 Successfully deployed to developer sandbox es. |
… es/2913-domain-request-screenreader
🥳 Successfully deployed to developer sandbox es. |
Ticket
Resolves #2913
Changes
Context for reviewers
Setup
With org model feature turned off, go to a domain request form and verify that all screenreader outputs match the subissues.
Code Review Verification Steps
As the original developer, I have
Satisfied acceptance criteria and met development standards
Ensured code standards are met (Original Developer)
Validated user-facing changes (if applicable)
As a code reviewer, I have
Reviewed, tested, and left feedback about the changes
Validated user-facing changes as a developer
Note: Multiple code reviewers can share the checklists above, a second reviewer should not make a duplicate checklist. All checks should be checked before approving, even those labeled N/A.
As a designer reviewer, I have
Verified that the changes match the design intention
Validated user-facing changes as a designer
References
Screenshots