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.

Sign up for GitHub

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

Jump to bottom

Add accessibility section #327

Closed
LJWatson opened this issue Apr 9, 2020 · 9 comments · Fixed by #328
Closed

Add accessibility section #327

LJWatson opened this issue Apr 9, 2020 · 9 comments · Fixed by #328
Assignees
@inexorabletash
Labels
a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response. has-pr
Milestone
V3

Comments

@LJWatson
Copy link

LJWatson commented Apr 9, 2020

In the WebApps charter it says:

Where there are implications for implementors, developers, or users, in the areas of accessibility, internationalization, privacy, and security, each specification must have a section that describes relevant benefits, limitations, and best practice solutions for that particular area.>

To this end each spec needs to have an accessibility section. For the avoidance of doubt in the reader, the section should be included even if it indicates there are no known accessibility considerations.

Relates to w3c/webappswg#15
@inexorabletash inexorabletash self-assigned this Apr 9, 2020
@inexorabletash inexorabletash added this to the V3 milestone Apr 9, 2020
@inexorabletash
Copy link
Member

It should also have an Internationalization section, to round out the horizontals.

Are there any good templates to follow, or existing specs that speak to accessibility concerns well, especially for similar pure-API standards with no expected UI?

inexorabletash added a commit that referenced this issue Apr 9, 2020
@inexorabletash
Add accessibility section draft. Resolves #327
1ab41cf
@inexorabletash inexorabletash mentioned this issue Apr 9, 2020
Merged
1 task
@LJWatson
Copy link
Author

We're blazing a bit of a trail on this. For an API like this where there is definitely no impact on the UI/accessibility, I'd suggest an "Accessibility" heading followed by a very short and simple section that says something like the following:

This specification has no impact on the user interface and therefore there are no accessibility considerations for implementors, developers or users.>

@akuckartz
Copy link

For an API like this where there is definitely no impact on the UI/accessibility ...

Are there any checklists regarding potential accessibility impacts of APIs?

@LJWatson
Copy link
Author

There is the Framework for Accessible Specification of Technologies (FAST) with an associated FAST checklist.

Worth noting that in 2016 the APA WG (that does horizontal review for accessibility) decided that this spec did not need accessibility review, presumably (if my memory serves) because it has no impact on the UI.

@inexorabletash
Copy link
Member

Awesome, thanks for the links. The checklist will provide a good format, even if mostly enumerating that this API does not have most of the relevant features.

Note that user agents are likely to have some user interface elements associated with storage APIs even when the storage APIs do not define them - such as developer tools, or for end users to see which sites are storing data. I called that out in a draft PR.

@inexorabletash
Copy link
Member

Updated draft, direct link to the new accessibility section is https://pr-preview.s3.amazonaws.com/w3c/IndexedDB/pull/328.html#accessibility

inexorabletash added a commit that referenced this issue Apr 14, 2020
@inexorabletash
Add accessibility section draft. Resolves #327
40eb558
inexorabletash added a commit that referenced this issue May 19, 2020
@inexorabletash
Add accessibility section draft. Resolves #327
a69534f
inexorabletash added a commit that referenced this issue May 21, 2020
@inexorabletash
Add accessibility section draft. Resolves #327
f77d89c
inexorabletash added a commit that referenced this issue May 21, 2020
@inexorabletash
git squash commit for a11y.
0048f99 
f77d89c
Add accessibility section draft. Resolves #327

822a7ae
Flesh out A11y section using draft FAST checklist https://w3c.github.io/apa/fast/checklist.html
@inexorabletash inexorabletash added the a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response. label Jun 30, 2020
@inexorabletash
Copy link
Member

Anyone want to review the PR?

@pwnall
Copy link

pwnall commented Jun 30, 2020

@inexorabletash Done.

inexorabletash added a commit that referenced this issue Jun 30, 2020
@inexorabletash
Add accessibility concerns section
59eeeb6 
Assembled using the very helpful draft FAST checklist https://w3c.github.io/apa/fast/checklist.html

Resolves #327
@LJWatson
Copy link
Author

The accessibility section is terrific! Thanks @inexorabletash

@garykac garykac mentioned this issue Aug 4, 2020
Open
@inexorabletash inexorabletash mentioned this issue Sep 28, 2020
Closed
inexorabletash added a commit that referenced this issue Feb 1, 2021
@inexorabletash
Add accessibility concerns section
7efa8d6 
Assembled using the very helpful draft FAST checklist https://w3c.github.io/apa/fast/checklist.html

Resolves #327
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@inexorabletash inexorabletash

Labels
a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response. has-pr
Projects
None yet
Milestone
V3
Development

Successfully merging a pull request may close this issue.

Add accessibility section draft. w3c/IndexedDB
4 participants
@pwnall @akuckartz @inexorabletash @LJWatson