Open lfdebrux opened 4 years ago
I've added a checklist for all the places where we use the summary table; I've ticked off the ones which don't seem to have a button or a link.
We have an existing pattern for this that probably got missed when building the admin tools, a hidden_text
attribute on summary.edit_link
where extra context can be added for screen readers: https://github.com/alphagov/digitalmarketplace-briefs-frontend/blob/master/app/templates/buyers/section_summary.html#L75
When we have a summary table with a number of buttons/links we tend to repeat the link and expect a user to be able to associate the button with the text of the row.
However, for a user using a screenreader, these button/link names are ambiguous and unclear.
For screenreaders to be able to give users context on what a link or button actually does we need to include hidden text to expand on what the button does.
Checklist
app/templates/view_suppliers.html
app/templates/view_supplier_services.html
app/templates/view_agreements_list.html
app/templates/supplier_details.html
app/templates/view_statistics.html
app/templates/view_service.html
app/templates/view_buyers.html
app/templates/service_updates_unapproved.html
app/templates/view_admin_users.html
app/templates/view_users.html
app/templates/view_agreements.html
app/templates/view_supplier_users.html
app/templates/manage_communications.html
app/templates/suppliers/_declaration_pass_fail.html
app/templates/suppliers/_frameworks_table.html
app/templates/suppliers/view_declaration.html
app/templates/suppliers/_company_details_table.html
app/templates/suppliers/upload_countersigned_agreement.html