nhcarrigan/library
9
0
Fork 0
generated from nhcarrigan/template
Code Issues Pull Requests 54 Actions Releases 3 Activity

[FEATURE] - Accessibility Audit and Improvements #53

New Issue
Closed
opened 2026-02-19 16:42:02 -08:00 by naomi · 0 comments
naomi commented 2026-02-19 16:42:02 -08:00
Owner
Copy Link
Copy Source

Attestations

  • I have read and agree to the Code of Conduct
  • I have read and agree to the Community Guidelines.
  • I have confirmed that the issue I am opening is unique, and has not already been reported (whether closed or not).
  • I have reviewed the Security Policy and have determined that this is not a security vulnerability.
  • This is not a feature request or bug report that I am mis-filing to avoid the issue template.

Share your thoughts:

Conduct a comprehensive accessibility audit of the application and implement improvements to ensure the library is usable by everyone.

Audit Areas

Keyboard Navigation

  • Ensure all interactive elements are keyboard accessible
  • Verify logical tab order throughout the app
  • Add visible focus indicators
  • Test all features work without a mouse

Screen Reader Support

  • Add proper ARIA labels and roles
  • Ensure alt text on all images
  • Use semantic HTML elements
  • Test with popular screen readers (NVDA, JAWS, VoiceOver)

Visual Accessibility

  • Ensure sufficient colour contrast (WCAG AA minimum)
  • Support browser zoom up to 200%
  • Avoid relying solely on colour to convey information
  • Test with colour blindness simulators

Form Accessibility

  • Associate labels with form inputs
  • Provide clear error messages
  • Use fieldsets and legends for grouped inputs
  • Add helpful placeholder text and hints

Content Accessibility

  • Use clear, descriptive headings
  • Maintain proper heading hierarchy (h1 → h2 → h3)
  • Provide skip navigation links
  • Ensure text is readable and well-structured

Tools to Use

  • Lighthouse accessibility audit
  • axe DevTools
  • WAVE browser extension
  • Manual keyboard testing
  • Screen reader testing

Success Criteria

  • Pass WCAG 2.1 Level AA compliance
  • Lighthouse accessibility score of 95+
  • All critical issues resolved
  • Documentation of accessibility features

✨ This issue was created with help from Hikari~ 🌸

### Attestations - [x] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/) - [x] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/). - [x] I have confirmed that the issue I am opening is unique, and has not already been reported (whether closed or not). - [x] I have reviewed the [Security Policy](https://docs.nhcarrigan.com/legal/security/) and have determined that this is not a security vulnerability. - [x] This is not a feature request or bug report that I am mis-filing to avoid the issue template. ### Share your thoughts: Conduct a comprehensive accessibility audit of the application and implement improvements to ensure the library is usable by everyone. ## Audit Areas ### Keyboard Navigation - Ensure all interactive elements are keyboard accessible - Verify logical tab order throughout the app - Add visible focus indicators - Test all features work without a mouse ### Screen Reader Support - Add proper ARIA labels and roles - Ensure alt text on all images - Use semantic HTML elements - Test with popular screen readers (NVDA, JAWS, VoiceOver) ### Visual Accessibility - Ensure sufficient colour contrast (WCAG AA minimum) - Support browser zoom up to 200% - Avoid relying solely on colour to convey information - Test with colour blindness simulators ### Form Accessibility - Associate labels with form inputs - Provide clear error messages - Use fieldsets and legends for grouped inputs - Add helpful placeholder text and hints ### Content Accessibility - Use clear, descriptive headings - Maintain proper heading hierarchy (h1 → h2 → h3) - Provide skip navigation links - Ensure text is readable and well-structured ## Tools to Use - Lighthouse accessibility audit - axe DevTools - WAVE browser extension - Manual keyboard testing - Screen reader testing ## Success Criteria - Pass WCAG 2.1 Level AA compliance - Lighthouse accessibility score of 95+ - All critical issues resolved - Documentation of accessibility features ✨ This issue was created with help from Hikari~ 🌸
naomi closed this issue 2026-02-20 01:51:25 -08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/library#53
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?