Skip to content
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

screenreader now capable of reading checkbox group #12559

Merged
merged 5 commits into from
Nov 4, 2019

Conversation

ajspotts
Copy link
Contributor

@ajspotts ajspotts commented Nov 1, 2019

Resolves #{12123}

Description

Enables users who utilize assistive technology to identify the name of the group ("Special Issues") that the checkboxes are located in by adding elements <fieldset> & <legend> identified by W3C standards as readable by a screenreader

@ajspotts ajspotts requested a review from lomky November 1, 2019 20:51
@codeclimate
Copy link

codeclimate bot commented Nov 1, 2019

Code Climate has analyzed commit ada6341 and detected 0 issues on this pull request.

View more on Code Climate.

@ajspotts ajspotts removed the request for review from lomky November 1, 2019 21:06
})
}
</div>
<fieldset style={{ width: '100%' }}>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Styling should probably be put into a variable elsewhere, then injected via that variable.

</p>
<TabWindow tabs={tabs} onChange={this.onTabSelected} />
</div>
)}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is everything above this line just formatting? Was having a hard time seeing any other differences.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, had to re-formate after initial commit to undo changes from Prettier extension hence all the changes. Sorry for the confusion!

Copy link
Contributor

@kevmo kevmo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the best way to test this?

I would add a note in the PR description that you also spruced up formatting.

The failing spec that is about jobs is likely a flake. The 2 feature tests that failed bear examining.

Copy link
Contributor

@kevmo kevmo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

@ajspotts ajspotts added the Ready-to-Merge This PR is ready to be merged and will be picked up by va-bot to automatically merge to master label Nov 4, 2019
@va-bot va-bot merged commit 0984143 into master Nov 4, 2019
@va-bot va-bot deleted the 12123-Dispatch-Special-Issues-checkboxes branch November 4, 2019 21:05
@alisan16
Copy link
Contributor

alisan16 commented Nov 5, 2019

Looks awesome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ready-to-Merge This PR is ready to be merged and will be picked up by va-bot to automatically merge to master
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants