![]() ![]() Ensure containing elements allow text resize without loss of functionality.Ensure custom controls provide proper textual name, role, and state information - 33% occurrence rate.Provide a valid label for form fields - 27% occurrence rate.Provide an informative, context-sensitive page title - 60% of our page titles did not have accurate titles.Ensure the reading order of content and elements are correct when viewed without style sheets.Ensure color is not the sole means of indicating error messages.Ensure form field constraints and errors are associated with their corresponding field.Along with this change, we were able to standardize how announcements are being made, which should make it easier to avoid this violation moving forward.If a job shows up multiple times on a page, and the job is favorited in one area, an announcement will now be made to users with screen readers that the other parts of the UI are updated.Apply aria-live regions for favorite buttons (falls within Ensure custom controls provide proper textual name in the accessibility audit).This will allow us to keep our form components accessible moving forward. Provide fieldsets for groups of form controls - all of our common form components, specifically RadioButtonList, CheckboxList, MonthYearSelect, and Pills, are properly grouped within fieldsets.Ensure ARIA roles, states, and properties are valid.Ensure color is not used as the sole method of indicating selection.Avoid inappropriate use of ARIA roles, states, and properties.Ensure that keyboard focus remains within modal dialogs.Provide fieldsets for groups of form controls.Ensure custom controls provide proper textual name, role, and state information.Inform assistive technologies of changes in content.Ensure page tabs provide state and role.Ensure custom controls are keyboard accessible.Complete work for: Ensure page tabs provide state and role.Provide a clear indication of fields in error for information that is submitted.Ensure error messages are explicitly indicated at the beginning of a form after submit.Ensure content is visible to assistive technologies.Avoid use of placeholder values or explain input.Ensure headings and labels are descriptive and unique.Ensure markup documents contain well-formed elements.Ensure Javascript functionality is accessible from the keyboard.Ensure link text is meaningful within context.Ensure keyboard focus returns properly when menus are closed.Ensure charts and graphs provide an informative and visible alternative description.Ensure CSS background images that convey meaning have textual and visible equivalents.Ensure alternative text for image links is informative.Ensure implicit row header cells use elements with row scope.Ensure that instructive text is placed at the beginning of a form.Provide error prevention for legal commitments, financial transactions, test responses, and data changes.Ensure text and images of text provide sufficient contrast.Provide visual labels or instructions for user input.Provide visual or instructions for user input.Ensure heading level matches the heading’s visual importance/level.Avoid unnecessary use of heading elements. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |