- Enable browsers and technical aids to identify lists and then reproduce them accurately, in order to facilitate their understanding by users.
- Improve the semantics of page content and its reusability.
- Improve the accessibility of content for people with disabilities.
Either use the appropriate HTML elements:
ul, lifor unordered listings;
ol, lifor ordered listings;
dl, dt, ddfor listings of definitions or descriptions.
Or use the ARIA attributes to give the semantics of an unordered or ordered listing with more generically tagged content:
- give the listing container a
- give each element of the list a
- (there is no equivalent to definition listings via an ARIA role).
Find out more:
For each page containing a listing:
- Check the source code of content presented in listing form (characterised by the presence of line breaks and list markers such as bullets or numbers) using a code inspector.
- Check whether the source code of these visible listings includes the HTML elements corresponding to the type of listing in question:
ul, lifor an unordered listing (bulleted listing),
ol, lifor an ordered listing (numbered listing) and
dl, dt, ddfor a listing of definitions or, failing that, the ARIA roles
Business application and benefits
The rules should be applied to your projects from the design phase through to post-implementation , and they should be understood by all professionals with web and customer experience (CX) responsibilities: from strategy to operations, marketers to project managers, and editorial to technical staff. The benefits of using this ruleset are numerous, including improving customer satisfaction, web performance, and e-commerce, and expanding your client base, while also decreasing your errors and costs.
The objective of these rules and the Opquast community mission is ‘making the web better’ for your customers and for everyone! Opquast rules cover the key major areas of risk that can negatively affect website users such as privacy, ecodesign, accessibility and security.