Post by Lux on Jun 1, 2023 0:10:45 GMT 1
Making Accessible Forum Posts
In light of the recent announcement on the SCF discord server's #announcement channel regarding ableism and discriminatory comments disabled people. I have decided to create this thread to guide people on how to consider web accessibility when creating forum posts, as disability discrimination is more than just ableist comments, it is also making inaccessible forum posts. For example, those who use screen readers may struggle reading some forum posts. This is backed up the Web Content Accessibility Guidelines (WCAG) which is recognised by laws in some countries and unions, such as the USA, the EU, the UK, Canada, Australia and Israel. More information of these guidelines can found on their wikipedia page (Web Content Accessibility Guidelines) or their website (Overview of WCAG 2 Guidelines), which is more exhaustive. In addition, Worcestershire's County Council created the acronym, 'SCULPT' in regard to creating inclusive documents and forum posts, more information on this is linked on their website (About SCULPT for Accessibility, Worcestershire County Council). The acronym provides a basic overview on the different features of documents (and posts), how they can become more inclusive and why it is important. The acronym stands for:
- Structure - using headings and styles features. This is unfortunately not the most applicable on the forums, due to the limited functionality. But try and make the different features of a post (headings, body text) distinguishable by using font sizes and bolding. More information is linked via Structure of a document and how headings work. (Worcestershire County Council).
- Colour Contrasts - Use the appropriate colour contrasts, using colours that are too similar with each other, may make it difficult for users to read. To check if the colour contrast is accessible and suitable, I would recommend using WebAIM's Colour Contrast Checker (hyperlink). I would also advise against using gradients as backgrounds for text, as it can be confusing for some readers. If you feel the need to use gradients for backgrounds, aim to the gradient as subtle as possible. I would also recommend avoid using just black and white, where possible. More information can be found via Colour and Contrast (Worcestershire County Council).
- Use of Images (and Visual Content) - Besides from images, this also includes shapes, charts and videos. When using images and other visual content, you only should only use it when supporting the text. When you have to use it, you should not use them to substitute text, you should use the correct image sizes (It is best to keep them 150kb, where possible) and use alternative (alt) text on images (There is functionality on the forums under 'Insert Image' tab to add alt text.). If it not possible to use alt text (for example, an embedded video), it is recommended to use caption instead to explain what the video is. More information can be found via Use of Images - adding meaningful alt text. (Worcestershire County Council).
- Links (Hyperlinks) - Links should be explained and descriptive, so those with screen readers can understand where the hyperlink directs them to. Best practice for this includes, not using the full web address, not using phrases similar to 'click me' in the hyperlink and describing where the link is actually going to (use the title of the webpage and the name of the organisation who runs the website). Please also ensure the colour of the link is distinguishable from the main body of text. More information can be found via Links - describing hyperlinks helpfully. (Worcestershire County Council).
- Plain English: Plain English needs to be clear and concise and with the right tone of voice. It should not contain complex language, long words and unexplained acronyms. This is useful for individuals with learning or cognitive disabilities or individuals whose English is not their first language. More information can be found via Plain English - using clear language and avoiding jargon (Worcestershire County Council).
- Table Structure: Tables should only be used when necessary, such as for data entry and should not not be used for document layouts. Accessible tables should not contain merged, split and blank cells, as it can be confusing for those who use screen readers. They should also not include tables within tables. More information can be found via Tables - Structure of tables for accessibility. (Worcestershire County Council).
A poster styled graphic of the 'SCULPT' acronym (hyperlink (.pdf)) has been created by Worcester County Council simplifies this more.
It is important to recognise that SCULPT does not consider all elements of web and document accessibility and therefore, I can provide additional recommendations to make your forum posts more accessible. This includes:
- Font Face - Use sans-serif fonts (those without flourishes) for main body of text, as serif (flourished) fonts can be confusing for some readers, such as those with dyslexia. Serif fonts can be used for titles and headings but it is always recommended to choose sans-serif fonts over them. I can also recommend avoiding using the Raleway font, as it can be inaccessible to read for some neurodivergent and dyslexic readers. Best alternatives to use are Karla and Poppins.
- Font Size - Use 3 (12pt), as the default, especially for main body text. Use 6 (24pt) or 7 (36pt) for main titles and headings. Subheadings and subtitles should be any of the sizes in between the default and main titles.
- Font Effects (Bold, Italics, Underline, Strike-Through) - For best practice use bolding to emphasise text. Avoid using the other effects where possible and when necessary, as it can be confusing for some readers.
- Text Alignment - Text should be generally left-aligned/justified for easier readability, especially for main body text. However, titles and headings can be centre-aligned/justified.
- Bullet Points - Use the automated bullet point feature on ProBoards when making lists rather than creating them manually, as this is easier for screen readers to navigate.
- Embeds (such as Spotify, Instagram) - Caption them with the title of the post for social media posts and state which social media it is from. For Spotify, include the song title and artist name within the caption as well as stating it is from Spotify.
Important Notes:
Disclaimer, it is also important to understand people are not perfect. It is okay to make mistakes with digital accessibility/web design, as long as you hold yourself accountable and learn from your mistakes. Don't worry if you don't get it right the first time.
There is no end goal for inclusive web practice, it is about being progressive and adaptive to include everyone in the changing environment. WCAG are constantly changing, with its next update expected to be released end of this year.
If you want further information regarding this, DigitalA11y has a Digital Accessibility Resources hub (DigitalA11y website), which has a list of resources you can use to improve digital accessibility knowledge.
If you have any suggestions or amendments to this post, feel free to let me know by replying below or messaging me via Forum or Discord private message.
• FC 
• Own Song Contests 
• EoF 
• BMF 
• SSC 
• MSC 
