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

WCAG: Input Assistance #342

Closed
StephDriver opened this issue Mar 8, 2024 · 1 comment
Closed

WCAG: Input Assistance #342

StephDriver opened this issue Mar 8, 2024 · 1 comment
Assignees
Labels
a11y accessibility audit an inspection or deliberately search for issues.

Comments

@StephDriver
Copy link
Contributor

StephDriver commented Mar 8, 2024

Summary

This review considered:

  1. Error identification
  2. Labels or Instructions
  3. Error Suggestion
  4. Error Prevention
  5. Redundant Entry
  6. Accessible Authentication (minimum)

Audit Results

Error identification

Validation occurs on form submission. Error messages are displayed in text form, but there is a problem with timing and context as described in #338 and #333. This is being addressed there.

Labels or Instructions

User input is labelled and where appropriate placeholder text is used to show an example of input possible.
For the user profile settings page there some ambiguity between 'Salutation' and 'Name Prefix' Such that for example putting "Dr" in the first won't show up on the profile, but will if in the second. But it is unclear where these fields are being used, so a user cannot know which to use for what.

Doesn't show Dr in profile

image

Does show Dr in profile

image

Error Suggestion

The error for a failed login is appropriate for security in that it notifies of the failure and does not indicate whether an account exists for that user name.

Error Prevention

The only part of the website that handles legal and/or financial transactions is the supporter signup sheet. This needs further investigation as to whether it is compliant.

The site does allow login and signup for accounts, and there is validation on this data. Once logged in, users can access their profile with options to amend this data.

Redundant Entry

The only information previously provided by a user than must be re-entered is the username and password, which is essential for security.

Accessible Authentication (minimum)

email and password inputs are properly marked up as per H100.
Authentication of email for new signups is via email link authentication.

@StephDriver StephDriver added a11y accessibility audit an inspection or deliberately search for issues. labels Mar 8, 2024
@StephDriver StephDriver added this to the A11y Audit (launch) milestone Apr 10, 2024
@StephDriver StephDriver moved this to Debate in Accessibility Apr 12, 2024
@joemull
Copy link
Member

joemull commented Apr 29, 2024

I've added two issues to the summary above that will help satisfy these requirements.

@joemull joemull assigned StephDriver and unassigned joemull Apr 29, 2024
@github-project-automation github-project-automation bot moved this from Debate to Done in Accessibility Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y accessibility audit an inspection or deliberately search for issues.
Projects
Status: Done
Development

No branches or pull requests

2 participants