Accessibility testing #183
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#183
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
When testing the webpage/dashboard it needs to conform to accessibility standards, such as contrast and color combination. Hopefully HiS's colour palette is already color-combination-friendly but the use of different contrasts is on us, and needs to be tested. This can be done by using a contrast checker tool (like this one from WebAIM).
This is a high-level issue and should be applied to every front-end part.
It should also be added to the wiki as a part of the testing standards.
Once a frontend prototyp has been made, Google's Lighthouse might be of good use for this purpose.
WAVE Evaluation tool is an accessibility testing tool which tests the website for accessibility and Web Content Accessibility Guideline (WCAG) errors, it has a chrome extension and therefore works with our localhost
Aceit Accessibility Evaluator is an accessibility testing tool that tests the website for requirements from WCAG and EN 301 549. It tests the website page by page, however it doesn't give much details about the potential issues and to properly use it we need a product key. We can also only check the publicly available adress and not any test builds
Siteimprove is an accessibility tool which tests the website if it complies with WCAG requirements. It also has a chrome extenstion, however it is a little unintuitive.
The Wiki page is now done.
as it seems the research is done and wiki is updated. I close this issue.
Good research! But we need do come to a conclusion about what to use and update the wiki accordingly.
This is related to our issue of creating our new designs #843
I have made the conclusion part a bit clearer now, if you think the conclusion is too short or not sufficient then i can update it again.
@c24danli can you review his wiki and we can close this issue?
The research is good, but as im not sure about the testing i have some questions, we dont use Wave now right? do we use any other or is this purely for the future?
@c24danli wrote in #183 (comment):
@b24jonel you can answer better this question
@c24danli wrote in #183 (comment):
Currently no one is using any accessibility tool from what i know, so i think we should be using Wave but we aren't right now and it's too late to start now so i would say it's for the future and for next years students.
ok good as this is in the wiki Iwill close this issue now