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

[A11Y] Accessibility mega-issue #3360

Open
22 of 28 tasks
davwheat opened this issue Mar 3, 2021 · 3 comments
Open
22 of 28 tasks

[A11Y] Accessibility mega-issue #3360

davwheat opened this issue Mar 3, 2021 · 3 comments
Assignees
Labels
type/accessibility Issues relating to accessibility (keyboard navigation, screenreaders, text contrast, etc.)

Comments

@davwheat
Copy link
Member

davwheat commented Mar 3, 2021

Flarum isn't particularly accessible at the moment, particularly revolving around keyboard navigation.

This issue serves as progress tracking for individual a11y issues.

More issues may be present in core aside from just the ones listed below. If this is the case, please open an individual issue, and reference that issue as a reply to this issue. Discussion should also take place on individual issues rather than this issue.

Current issues (Core only)

Bundled extensions

@davwheat
Copy link
Member Author

I just discovered this: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions

We should probably look into a way to implement this, but I can't think of a great way, especially with extensions that might modify page content that we don't think about.

Setting aria-live="polite" on commonly modified areas (e.g. PostStreams) would be a great starting point.

@davwheat davwheat self-assigned this Mar 15, 2021
@davwheat davwheat added the type/accessibility Issues relating to accessibility (keyboard navigation, screenreaders, text contrast, etc.) label Mar 15, 2021
@SychO9
Copy link
Member

SychO9 commented Apr 21, 2021

I noticed the admin area form labels have no for attribute linking them to their inputs, the actual label attribute on the input isn't a thing, it's just leftover from not removing it from componentAttrs on JS side.

<div class="Form-group">
    <label>Forum Title</label>
    <div class="helpText"></div>
    <input type="text" label="Forum Title" class="FormControl">
</div>

Also, let's log #2799 as done as well.

@davwheat davwheat pinned this issue Oct 13, 2021
@askvortsov1 askvortsov1 transferred this issue from flarum/framework Mar 10, 2022
@davwheat davwheat transferred this issue from flarum/issue-archive Mar 28, 2022
@SychO9 SychO9 pinned this issue Jul 14, 2022
@azurejoga
Copy link

Hello, some unlabeled buttons such as the start a discussion button and the publish the post/discussion button after the title and after the write field these buttons are unlabeled, which file can I edit to fix these problems while a official fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/accessibility Issues relating to accessibility (keyboard navigation, screenreaders, text contrast, etc.)
Projects
None yet
Development

No branches or pull requests

3 participants