The Web is fundamentally designed to work for all people, whatever their hardware, software, language, location, or ability. When the Web meets this goal, it is accessible to people with a diverse range of hearing, movement, sight, and cognitive ability.
Thus, the impact of disability is radically changed on the Web because the Web removes barriers to communication and interaction that many people face in the physical world. However, when websites, web technologies, or web tools are badly designed, they can create barriers that exclude people from using the Web.
Quote from the W3C.
Use rich text Headings as indicators for sections and sub-sections in your guide. This not only provides hierarchical organization and formatting but also makes it easy for screen readers to scan and jump to different content areas.
Here is an example default 2x2 table with a header created within the rich text editor.
|Header A||Header B|
|cell A1||cell B1|
|cell A2||cell B2|
Take caution when copying & pasting content from any source. Many times hidden style code will also be copied along that could break with best practices and introduce inaccessible content.
There are a few ways to avoid hidden style code from being placed into your guide.
This will generally solve strange formatting issues you may find from copied text.
Video and audio content are a great supplement to any guide, but great care must be used to make sure embedded content is accessible.
All non-HTML content should be accessible. If you can't find or create accessible non-HTML content then consider using HTML instead.
Here are some guides and utilities that can aid you in constructing accessible documents.