We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is a good first issue for new contributors to take on, if you have any questions, please ask on the task or in our Gitter room!
Accessibility Lab recommendations:
A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. A mechanism for identifying the expanded form or meaning of abbreviations is available.
A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
A mechanism for identifying the expanded form or meaning of abbreviations is available.
WCAG 3.1.3 and 3.1.4 per #5972.
Suggested as part of #6211: Is digital-security and SecureDrop-specific jargon marked with <abbr title>, ideally drawing from the SecureDrop glossary?
<abbr title>
The text was updated successfully, but these errors were encountered:
I'm interested in taking this issue.
Sorry, something went wrong.
Since the ticket has not been closed I will add fixes for the comments made on the pull request and create a new one
I am picking this back up and will be resolving it
Successfully merging a pull request may close this issue.
This is a good first issue for new contributors to take on, if you have any questions, please ask on the task or in our Gitter room!
Description
Accessibility Lab recommendations:
User Research Evidence
WCAG 3.1.3 and 3.1.4 per #5972.
Implementation
Suggested as part of #6211: Is digital-security and SecureDrop-specific jargon marked with
<abbr title>
, ideally drawing from the SecureDrop glossary?The text was updated successfully, but these errors were encountered: