Skip to content

Issues: theappbusiness/accessibility-guidelines

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

20 Open 26 Closed
20 Open 26 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Is this still being maintained?
#117 opened Jul 5, 2022 by PhilAtKC
Summary of 1.4.13 is a bit ambiguous: "remain visible" usability-issue
#103 opened Jan 7, 2020 by jfhector
Small readability issues on overview page usability-issue
#102 opened Jan 7, 2020 by jfhector
@jfhector
Ambiguity re. whether and how 1.4.2 'Page title' applies to native mobile apps usability-issue
#101 opened Jan 2, 2020 by jfhector
4
1.4.13: 'Dismissable' requirement probably worded in a way that's too restrictive
#100 opened Jan 2, 2020 by jfhector
@jfhector
1.3.3. header 'Sensory characteristics' isn't immediately clear usability-issue
#90 opened Dec 5, 2019 by jfhector
SC1.4.13: "... and remain visible" in the summary likely to be confusing
#89 opened Dec 4, 2019 by jfhector
'Resize text' (and some other 2.1 guidelines) might be web only
#88 opened Dec 4, 2019 by jfhector
SC 2.1 - Lack of wider understanding that keyboards are used to navigate native apps
#81 opened Dec 3, 2019 by robert-kinder
Clarify requirements for 1.3.5 Input purpose Android bug Something isn't working iOS review needed Review existing content and flag any issue
#63 opened Nov 18, 2019 by jfhector
Web implementation guidance and review needed for 1.3.1 'Structure and relationships' content needed good first issue Good for newcomers review needed Review existing content and flag any issue web
#59 opened Nov 17, 2019 by jfhector
Design guidance content needed for 1.3.1 content needed design good first issue Good for newcomers usability-issue
#58 opened Nov 17, 2019 by jfhector
1
SC1.3.2 Name 'Order of element in code' wrongly suggests that it's not the remit of designers to avoid that issue good first issue Good for newcomers
#54 opened Nov 16, 2019 by jfhector
SC4.1.2: Clarify it for designers, use plainer language good first issue Good for newcomers usability-issue
#45 opened Oct 29, 2019 by jfhector
1
SC3.2.1: Some designers didn't understand what the SC meant just by looking at the headline summary usability-issue
#39 opened Oct 29, 2019 by jfhector
2
SC1.4.12: Some designers not confident that they understood the SC just from the headline summary usability-issue
#37 opened Oct 29, 2019 by jfhector
@jfhector
6
SC1.3.5 headline summary Not understood by some designers usability-issue
#35 opened Oct 29, 2019 by jfhector
SC1.2.3 headline summary: Some designers confused about how SC1.2.3 differs from SC1.2.5 usability-issue
#32 opened Oct 29, 2019 by jfhector
"Make sure every task can be completed using just a keyboard" on iOS
#10 opened Aug 13, 2019 by KaneCheshire
@jfhector
3
"CSS" is not platform agnostic for the overview/summary page
#7 opened Aug 13, 2019 by KaneCheshire
@jfhector
7
ProTip! Follow long discussions with comments:>50.