Producing accessible PDF documents requires to follow recommendations to make sure they are structured through proper tagging, to make them understandable and useable by everyone (including users with assistive technology).
\n-
Below are listed guides aiming at providing necessary information in order to manually create accessible PDF documents based on the most popular softwares, then we will list the mandatory criteria to follow for PDF accessibility.
This document was produced by AcceDe PDF phase 1 (2011), driven by Atalan together with 9 enterprises: Spie, Air Liquide, Société Générale, BNP Paribas, Areva, LVMH, Capgemini, Thales et SNCF, who relied on a review team made up of numerous professionals and organisations involved in digital accessibility.
This document was produced by AcceDe PDF phase 2 (2015), driven by Atalan together with Orange and 9 other enterprises: La Poste, Siemens, Spie, Thales, Atos, BNP Paribas, Devoteam, Manpower and EDF, who relied on a review team made up of numerous professionals and organisations involved in digital accessibility.
\n-
Mandatory criteria
\n-
The following are the main criteria for a PDF document to be accessible, regardless of the method used to create it. Mandatory criteria will be useful for people creating PDF documents even when they don’t rely on publication software (Microsoft Word, Adobe InDesign, Adobe Acrobat Pro), e.g. developers whose applications generate PDF documents.
\n-
Document structure
\n-
Le document doit contenir a minima un titre de document et une langue par défaut (les changements de langues seront indiqués dans le document).
\n-
The document must at the very least include a document title and a default language (language changes must be indicated in the document).
The document is structured with titles, through the proper use of title “tags”. Moreover, long documents must include bookmarks to make navigation easier.
The reading order conveyed by an assistive tool, as well as keyboard navigation (through tabbing) must reflect the document’s structure. There must be no keyboard trap (keybaord navigation must be possible in the whole document without any blocking point).
Images featuring information must have an appropriate alternative. Scanned documents must be covnerted to text through optical character recognition (OCR). Decorational images must be hidden.
A data table must be structured by a table “tag” containing at least one line. Table headers must be used appropriately. All lines must contain the same number of cells. Merged cells must clearly indicate if the merge was vertical or horizontal (rowSpan or colSpan attribute).
Lists must use the appropriate “tags”: list tag L, list item tag LI, list item label tag Lbl (for instance the item number, or the Lbody content tag of the list item).
Form fields must have a name, a role, a value, and a state (if needed). Visually, labels must be correctly positioned towards the field. Mandatory fields and expected formats must be indicated. Fields must be accessible and keyboard-modifiable. Forms that can be submitted must provide a submit button.
run automatic tests on a PDF document and check for accessibility issues,\n-
\n-
pre-visualise the document the way it will be presented to assistive tools, so as to check the reading order and the semantics used (title, paragraph, …),
\n-
give access to a detailed view of the accessible information given to an assistive tool.
\n-
\n-\n-
Creating accessible PowerPoint documents
\n-\n-\n-\n-\n-
Introduction
\n-
To produce accessible PowerPoint documents, one has to follow recommendations. Fortunately, PowerPoint comes equipped with a tool to check accessibility.\n-It pinpoints the main issues and suggests solutions to remedy them.
\n-
This being said, even after correcting said issues, we realised that some elements (SmartArt, tables, …) were not always correctly vocalised by screen readers.\n-This is why, when your presentation is done, we recommend to export it in PDF before broadcasting the document: the Export option in PowerPoint gives better results with assistive technologies; also it removes animations, which are often a problem for people with vision problems.
\n-
Recommendations
\n-
Below you will find a summary of recommendations that provide better accessibility with PowerPoint.\n-For more information, please refer to the guides provided on the DINSIC website (in French).
\n-
Our tests were done using Office 2010 with Jaws 17 and NVDA 2017-1. The below recommendations are the result of these tests.
\n-
1. Use slide masks
\n-
Presentations must be created using slide masks (menu: Display > Slide masks). Then use checkboxes “Title”, “Footers”, and the menu “Insert reserved space”.
\n-
2. Check the reading order of elements
\n-
The reading order must be checked through the Selection pane (menu Home > Organise > Selection pane). Be careful: the last element in the list is the first read by screen readers: the reading order must thus be from bottom to top in your slide masks.
\n-
3. Give a unique title to each slide
\n-
Each slide must have a unique title. This must be added in the zone titled “Click to add a title”.
\n-
4. Provide replacement text for images
\n-
If the image conveys information, you must provide a replacement text describing its content (right click, Image format > Replacement text > Description field).\n-If the image is strictly for decoration, the Description field must be left empty.
\n-
5. Make simple tables
\n-
Data tables must stay simple. Avoid blending cells together. Avoid inserting images: they will not be read as table elements but as independent elements which will be read before or after the table according to the internal document’s reading order. Leave no empty cell.
\n-
6. Use SmartArt rather than assembling text and shapes
\n-
SmartArt enables you to integrate images and text that will be vocalised in the proper order. All SmartArt clips are not correct yet, be careful.
\n-
7. Add a replacement text to graphics
\n-
The content of graphics must be described in the Replacement text for the graphic (Object format > Replacement text > Description).
\n-
8. Ensure colour is not the only means to convey information
\n-
Information given through colour must also be conveyed via another means like shape, position, size…
\n-
9. Ensure a sufficient contrast
\n-
Contrast between the colour of text and of its background must be sufficient:
Language must be defined through the menu: File > Options > Language.\n-Words or grops of words in another language must be explicitly described as such (menu: Revision > Language > Define the verification language).
\n-
11. Use the automated Accessibility checker
\n-
PowerPoint provides an Accessibility checker (menu File > Check for problems > Check accessibility). It lists all contents prone to be hard to deal with.
\n-
12. Exporting the presentation to PDF
\n-
To export to PDF you only need to go to File > Save as. Choose a name and select PDF as file type.\n-The first time, make sure that the “Accessibility-friendly document structure tags” checkbox in Export options is checked.
We tested the behaviour of NVDA (version 2017.1) and Jaws (version 17) under Windows with a PDF file generated with PowerPoint 2010.
\n-
Tables
\n-
Tables were vocalised correctly with Jaws and NVDA.
\n-
Tables with replacement text
\n-
NVDA: tables were still vocalised, replacement texts were ignored.\n-Jaws: tables were not vocalised any more, replacement texts were ignored.
\n-
SmartArt
\n-
Same behaviour for Jaws and NVDA: SmartArt texts were vocalised (not always in the proper order though).
\n-
SmartArt with replacement texts
\n-
NVDA: expected behaviour, replacement texts were read instead of the SmartArt.\n-Jaws: SmartArt were not vocalised any more, replacement texts were ignored.
\n-
Graphics
\n-
Jaws and NVDA had the same behaviour: figures in graphics were vocalised.
\n-
Graphics with replacement texts
\n-
Jaws and NVDA behaved as expected: replacement texts were vocalised instead of the graphics.
\n-\n-
Videos, audios, and animated components
\n-\n-\n-\n-\n-
Introduction
\n-
All pre-recorded videos should have a transcript attached and closed captions available, and audio description available when necessary.
\n-
Provide a transcript
\n-
Transcripts include the text of the words spoken in the video, and also the text of important words that appear on screen and important actions or changes of scene. It must be provided in text, HTML (to be preferred) or Word and must be immediately after the video.
\n-
Perimeter: all.
\n-
Provide captions
\n-
Captions are a text version of the speech and sound on the video. They are displayed over the video. Captions should appear at the same time as the sound they are captioning and appear onscreen long enough to be read. Closed captions have to be preferred over open captions as they can be set on or off by the viewer while open captions are displayed to all viewers. They are mainly needed for users with hearing disabilities.
\n-
Perimeter: videos, animated components.
\n-
Provide audio descriptions when important visual information is not covered in what is said
\n-
Audio descriptions are separate audio tracks containing speech that describes the action, characters, and scenes of a video. It is played along with the video and it lets blind and vision-impaired users know what’s happening on the screen.
\n-
Audio description is not needed for talking heads only, or for text on slides as long as the slide text is included into what is said. Audio description might be needed for components like charts and diagrams.
\n-
Perimeter: videos, animated components.
\n-
Choose an accessible media Player
\n-
\n-
Captions and audio description supported
\n-
On/off command for captions, audio description and setup menu
\n-
Buttons and controls usable without a mouse and properly labeled
\n-
Accessible to keyboard-only users and screen reader users.
\n-
\n-
Media player must support captions, and audio descriptions. Users must be able to set these features on and off.
\n-
Users with disabilities may use navigational devices other than a mouse, such as keyboards or screen readers. For this reason, users should be able to operate the media player without using a mouse. The player should also label its buttons and controls, so that users with screen readers can hear the name of each button and control and select the correct option.
\n-
Perimeter: all.
\n-
Do not play videos automatically when the page loads
\n-
This can be confusing for many users, and the sound can interfere with assistive technologies such as screen readers.
\n-
Perimeter: all.
\n-
Do not use videos that have more than three flashes within a period of 1 second
\n-
This can provoke seizures in users with epilepsy.
\n-
Perimeter: videos, animated components.
\n-
All other relevant criteria such as color contrasts must also be enforced.
\n-
\n-
\n-\n-
Creating accessible Word documents
\n-\n-\n-\n-\n-
Introduction
\n-
Accessible Word documents are needed in order to be read by all users. Creating accessible Word documents requires to respect the following recommendations. It also enables you to produce accessible PDF documents through the PDF export functionality inside Word.
\n-
Recommendations
\n-
You will find below a summary of the recommendations to follow. For more detail, please refer to the DINSIC website (in French).
\n-
1. Use “Heading” styles for headings and sub-headings
\n-
Headings and sub-headings must use the “Headings” styles (Heading 1, Heading 2, etc.) to structure the document’s content and provide easy access to them.
\n-
2. Use the “Normal” style for texts
\n-
The “Normal” style must be used for all text paragraphs (default style).
\n-
3. Use dedicated styles to emphasize some contents.
\n-
Use predefined styles to emphasize some contents (e.g. quotes, legends, etc.) rather than using character formatting tools (bold etc.).
\n-
4. Don’t insert empty lines
\n-
Space between lines must be created through Paragraph options, where you can define the space before and after a paragraph.
\n-
Page jumps must be created via proper “Jumps” (Insert > Page jump, new page).
\n-
5. Use bulleted lists
\n-
Lists must be made using the option “Bulleted list” or “Numbered list”, and not by inserting dashes into the text.
\n-
6. Use footnotes
\n-
Options to insert “Footnotes” and “Endnotes” must be used to properly insert notes in your document.
\n-
7. Number your pages
\n-
The “Page number” option makes it easier to get one’s bearings in a document.
\n-
8. Use “Columns” to layout text
\n-
The “Columns” option in the Layout group must be used (instead of tables) to layout the page as proper columns.
\n-
9. Define the anchor for objects inserted into the page
\n-
When you insert objects (image, shape, SmartArt, etc.), it is necessary to define an anchor point: in the options for page flow, choose the option “Aligned on the text” or “Top and bottom”.
\n-
10. Avoid text zones
\n-
Floating text zones are not always properly read by screen readers. Texts can be emphasized through the use of borders around a paragraph, for instance.
\n-
11. Ensure colour is not the only means to convey information
\n-
Information given through colour must also be conveyed via another means like shape, position, size…
\n-
12. Ensure a sufficient contrast
\n-
Contrast between the colour of text and of its background must be sufficient:
Language must be defined through the menu: File > Options > Language.\n-Words or groups of words in another language must be explicitly described as such (menu: Revision > Language > Define the verification language).
\n-
14. Provide replacement text for images
\n-
If the image conveys information, you must provide a replacement text describing its content (right click, Image format > Replacement text > Description field).\n-If the image is strictly for decoration, the Description field must be left empty.
\n-
15. Make simple tables
\n-
Data tables must stay simple. Avoid blending cells together. Avoid inserting images: they will not be read as table elements but as independent elements which will be read before or after the table according to the internal document’s reading order. Leave no empty cell.
\n-
16. Use the automated Accessibility checker
\n-
Word provides an Accessibility checker (menu File > Check for problems > Check accessibility). It lists all contents prone to be hard to deal with and automatically detects failures. This tool must be used as it provides a huge help; however it does not prevent you from checking and applying all the recommendations provided in this page.
\n-
17. Exporting the document to PDF
\n-
To export to PDF you only need to go to File > Save as. Choose a name and select PDF as file type.\n-The first time, make sure that the “Accessibility-friendly document structure tags” checkbox in Export options is checked.
\n-
Please note that in Word for Office 2010 generated PDF documents can show accessibility issues, e.g. for the vocalisation of images. These issues were corrected in the following versions of Microsoft Office.
\n-
18. Insert an table of contents
\n-
For any long document (more than 2 pages), insert an automatically generated table of contents, in the menu & nbsp ;: References & nbsp;> Table of contents.\n-It makes easier for everyone to find their way around and quickly go to the content you want to read.
\n-
Note that you must update this table of contents as soon as you change the structure of the content, so prefer to generate the table of contents at the end of the content modifications.
\n- \n-\n- \n- \n- \n- \n- \n- \n-\n-\n\\ No newline at end of file"},{"sha":"fc252016f31db7912e0bb27fd7ec7b9ef1ca4306","filename":"others_EN/output/markdown/PDF.md","status":"removed","additions":0,"deletions":114,"changes":114,"blob_url":"https://github.com/Orange-OpenSource/a11y-guidelines/blob/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2FPDF.md","raw_url":"https://github.com/Orange-OpenSource/a11y-guidelines/raw/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2FPDF.md","contents_url":"https://api.github.com/repos/Orange-OpenSource/a11y-guidelines/contents/others_EN%2Foutput%2Fmarkdown%2FPDF.md?ref=969860377f2a87882b0ac0b4534619b0e1641641","patch":"@@ -1,114 +0,0 @@\n-# Creating accessible PDF documents\n-\n-\n-\n-\n-## Introduction\n-\n-Producing accessible PDF documents requires to follow recommendations to make sure they are structured through proper tagging, to make them understandable and useable by everyone (including users with assistive technology).\n-\n-Below are listed guides aiming at providing necessary information in order to manually create accessible PDF documents based on the most popular softwares, then we will list the mandatory criteria to follow for PDF accessibility.\n-\n-## Guides to create accessible PDF documents\n-\n-### With Microsoft Word\n-\n-You will find Microsoft Word recommendations as well as the PDF export procedure on our Creating accessible Word documents page.\n-\n-### With Adobe InDesign\n-\n-You will find Adobe InDesign recommendations (in French) at Créer des documents PDF accessibles avec Adobe Indesign by the AcceDe PDF initiative.\n-\n-This document was produced by AcceDe PDF phase 1 (2011), driven by Atalan together with 9 enterprises: Spie, Air Liquide, Société Générale, BNP Paribas, Areva, LVMH, Capgemini, Thales et SNCF, who relied on a review team made up of numerous professionals and organisations involved in digital accessibility.\n-\n-### With Adobe Acrobat Pro\n-\n-You will find Adobe Acrobat Pro recommendations at Making PDF documents accessible with Adobe Acrobat Pro by the AcceDe PDF initiative.\n-\n-This document was produced by AcceDe PDF phase 2 (2015), driven by Atalan together with Orange and 9 other enterprises: La Poste, Siemens, Spie, Thales, Atos, BNP Paribas, Devoteam, Manpower and EDF, who relied on a review team made up of numerous professionals and organisations involved in digital accessibility.\n-\n-## Mandatory criteria\n-\n-The following are the main criteria for a PDF document to be accessible, regardless of the method used to create it. Mandatory criteria will be useful for people creating PDF documents even when they don’t rely on publication software (Microsoft Word, Adobe InDesign, Adobe Acrobat Pro), e.g. developers whose applications generate PDF documents.\n-\n-### Document structure\n-\n-Le document doit contenir a minima un titre de document et une langue par défaut (les changements de langues seront indiqués dans le document).\n-\n-The document must at the very least include a document title and a default language (language changes must be indicated in the document).\n-\n-See PDF16, PDF17, PDF18.\n-\n-The document is structured with titles, through the proper use of title “tags”. Moreover, long documents must include bookmarks to make navigation easier.\n-\n-See PDF2, PDF9.\n-\n-The use of headers and footers must help the user locating themselves in the document.\n-\n-See PDF14.\n-\n-### Keyboard navigation and reading order\n-\n-The reading order conveyed by an assistive tool, as well as keyboard navigation (through tabbing) must reflect the document’s structure. There must be no keyboard trap (keybaord navigation must be possible in the whole document without any blocking point).\n-\n-See PDF3, G21.\n-\n-### Images\n-\n-Images featuring information must have an appropriate alternative. Scanned documents must be covnerted to text through optical character recognition (OCR). Decorational images must be hidden.\n-\n-See PDF1, PDF4, PDF7.\n-\n-### Tables\n-\n-A data table must be structured by a `table` “tag” containing at least one line. Table headers must be used appropriately. All lines must contain the same number of cells. Merged cells must clearly indicate if the merge was vertical or horizontal (`rowSpan` or `colSpan` attribute).\n-\n-SeePDF6.\n-\n-### Links\n-\n-Link texts must be explicit, or the links must provide an accessible alternative.\n-\n-See PDF11, PDF13.\n-\n-### Lists\n-\n-Lists must use the appropriate “tags”: list tag `L`, list item tag `LI`, list item label tag `Lbl` (for instance the item number, or the `Lbody` content tag of the list item).\n-\n-See PDF21, section 14.8.4.3.3 of the PDF specification.\n-\n-### Forms\n-\n-Form fields must have a name, a role, a value, and a state (if needed). Visually, labels must be correctly positioned towards the field. Mandatory fields and expected formats must be indicated. Fields must be accessible and keyboard-modifiable. Forms that can be submitted must provide a submit button.\n-\n-See PDF5, PDF10, PDF12, PDF15, PDF22.\n-\n-### Colours\n-\n-Colours must not be the only means to convey information.\n-\n-Contrast between the colour of text and of its background must be sufficient:\n-- 4.5:1 for normal-size text;\n-- 3:1 for bigger text.\n-\n-## Testing the accessibility of a PDF document\n-\n-Install PDF Accessibility Checker (PAC 2). \n-\n-This tool can, among other things:\n-\n-- run automatic tests on a PDF document and check for accessibility issues,\n-\n-\n-- pre-visualise the document the way it will be presented to assistive tools, so as to check the reading order and the semantics used (title, paragraph, …),\n-\n-- give access to a detailed view of the accessible information given to an assistive tool.\n-\n\\ No newline at end of file"},{"sha":"28d1de7c2c1f843c68ef2bfcfc9c6b2c83cca19b","filename":"others_EN/output/markdown/about.md","status":"removed","additions":0,"deletions":16,"changes":16,"blob_url":"https://github.com/Orange-OpenSource/a11y-guidelines/blob/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Fabout.md","raw_url":"https://github.com/Orange-OpenSource/a11y-guidelines/raw/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Fabout.md","contents_url":"https://api.github.com/repos/Orange-OpenSource/a11y-guidelines/contents/others_EN%2Foutput%2Fmarkdown%2Fabout.md?ref=969860377f2a87882b0ac0b4534619b0e1641641","patch":"@@ -1,16 +0,0 @@\n-# About \n-\n-\n-Documentation under the [CC BY SA 3.0 license](https://github.com/Orange-OpenSource/a11y-guidelines/blob/master/LICENSE), source code of this site and examples are available [on github](https://github.com/Orange-OpenSource/a11y-guidelines). \n-\n-The Orange logo and some images or screenshots are the property of Orange:\n-\n-Copyright (C) 2016 Orange SA All rights reserved \n-[List of the concerned files](/NOTICE.txt)\n-\n- \n-\n\\ No newline at end of file"},{"sha":"184c5c802b3631272d94e6e4e38447664b61d983","filename":"others_EN/output/markdown/contact.md","status":"removed","additions":0,"deletions":13,"changes":13,"blob_url":"https://github.com/Orange-OpenSource/a11y-guidelines/blob/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Fcontact.md","raw_url":"https://github.com/Orange-OpenSource/a11y-guidelines/raw/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Fcontact.md","contents_url":"https://api.github.com/repos/Orange-OpenSource/a11y-guidelines/contents/others_EN%2Foutput%2Fmarkdown%2Fcontact.md?ref=969860377f2a87882b0ac0b4534619b0e1641641","patch":"@@ -1,13 +0,0 @@\n-# Your opinion matters ... \n-\n-\n-Have a bug or a feature request? \n-\n-Please first check [the issues](https://github.com/Orange-OpenSource/a11y-guidelines/issues) and search for existing and closed issues. If your problem or idea is not addressed yet, please [open a new issue](https://github.com/Orange-OpenSource/a11y-guidelines/issues/new).\n-\n- \n-\n\\ No newline at end of file"},{"sha":"5155574d4a43eb0438831e1a723670ea3c332e52","filename":"others_EN/output/markdown/editorial.md","status":"removed","additions":0,"deletions":55,"changes":55,"blob_url":"https://github.com/Orange-OpenSource/a11y-guidelines/blob/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Feditorial.md","raw_url":"https://github.com/Orange-OpenSource/a11y-guidelines/raw/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Feditorial.md","contents_url":"https://api.github.com/repos/Orange-OpenSource/a11y-guidelines/contents/others_EN%2Foutput%2Fmarkdown%2Feditorial.md?ref=969860377f2a87882b0ac0b4534619b0e1641641","patch":"@@ -1,55 +0,0 @@\n-# General recommendations for content\n-\n-\n-\n-\n-## Introduction\n-This section proposes general recommendations to ensure your contents are accessible whatever the medium used (email, Web, Word, etc.).\n-\n-## Check colours\n-\n-- Make sure colour is not the only means used to convey information.\n-- Make sure there is sufficient contrast between the text colour and the background.\n-\n-The contrast can be checked with Colour Contrast Analyzer :\n- - 4.5:1 for normal size text.\n- - 3:1 for big text.\n-\n-## Facilitate reading\n-\n-- Align text to the left, don’t justify it.\n-- Use an easily-readable font family with a minimum size of 12 pixels.\n-- Use simple punctuation.\n-- Avoid italics, completely capitalised sentences; but always put a capital at the beginning of a sentence.\n-- Avoid textured backgrounds (images).\n-- Do not do too many repeated carriage returns or tabs to space contents (rather, use “Paragraph > Spacing” or “Indent” in Word for instance).\n-- Avoid layout and data tables.\n-- Avoid information-conveying content in images (graphs, schemas, diagrams,…)\n-- Signal the end of the document (for instance, an image saying “End of email”, or a white-on-white text “End of document”).\n-- Use simple, clear and short phrase turns: subject, verb, complement. One idea per sentence, with simple words.\n-- Explain complicated words.\n-- Use the present tense, preferably direct style, and active form (no subjunctive, no conjunctions).\n-- Use proper typographic characters: dash -, em-dash —, “rounded quotes”.\n- \n-- Avoid foreign words, abbreviations except those that are genuinely used.\n-\n-## Provide accessible layout tables\n-\n-Simplify tables, even if we know that email clients (including Outlook) still often demand to use tables for layout.\n-\n-Checkpoints:\n-\n-- In general, don’t do complex table layouts (merging cells, multicolumn,…).\n-- Avoid embedding layout tables (maximum two levels of embedding), but also:\n-- Don’t merge table cells, but use several simpler tables.\n-- Don’t keep empty cells.\n-- Don’t add background images.\n-- Make sure that the sequential order is correct (one can read left to right and top to bottom).\n-- Avoid complex data tables, graphs or schemas.\n-\n- \n-\n\\ No newline at end of file"},{"sha":"e69de29bb2d1d6434b8b29ae775ad8c2e48c5391","filename":"others_EN/output/markdown/images/.gitkeep","status":"removed","additions":0,"deletions":0,"changes":0,"blob_url":"https://github.com/Orange-OpenSource/a11y-guidelines/blob/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Fimages%2F.gitkeep","raw_url":"https://github.com/Orange-OpenSource/a11y-guidelines/raw/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Fimages%2F.gitkeep","contents_url":"https://api.github.com/repos/Orange-OpenSource/a11y-guidelines/contents/others_EN%2Foutput%2Fmarkdown%2Fimages%2F.gitkeep?ref=969860377f2a87882b0ac0b4534619b0e1641641"},{"sha":"7b5bb5b8cc51d3c81c7e580511f88bd98c736ceb","filename":"others_EN/output/markdown/index.md","status":"removed","additions":0,"deletions":27,"changes":27,"blob_url":"https://github.com/Orange-OpenSource/a11y-guidelines/blob/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Findex.md","raw_url":"https://github.com/Orange-OpenSource/a11y-guidelines/raw/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Findex.md","contents_url":"https://api.github.com/repos/Orange-OpenSource/a11y-guidelines/contents/others_EN%2Foutput%2Fmarkdown%2Findex.md?ref=969860377f2a87882b0ac0b4534619b0e1641641","patch":"@@ -1,27 +0,0 @@\n-# Accessibility recommendations Orange for content\n-\n-\n-\n-## General recommendations for content\n-The general recommendations describe the recommendations to respect whatever the type of content (web, email, Word document, etc.).\n-
\n-\n-## Specific recommendations by type of content\n-The following recommendations describe the specific rules to be followed depending on the type of document:\n-\n-- [Microsoft Word](./word.html) \n-\n-- [Microsoft PowerPoint](./powerpoint.html) \n-\n-- [PDF documents](./pdf.html) \n-\n-- [Videos, audios, and animated components](./video.html) \n-\n- \n-\n\\ No newline at end of file"},{"sha":"4e98fb34cb2198f596a0dc4ed3c12876f7c47788","filename":"others_EN/output/markdown/powerpoint.md","status":"removed","additions":0,"deletions":117,"changes":117,"blob_url":"https://github.com/Orange-OpenSource/a11y-guidelines/blob/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Fpowerpoint.md","raw_url":"https://github.com/Orange-OpenSource/a11y-guidelines/raw/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Fpowerpoint.md","contents_url":"https://api.github.com/repos/Orange-OpenSource/a11y-guidelines/contents/others_EN%2Foutput%2Fmarkdown%2Fpowerpoint.md?ref=969860377f2a87882b0ac0b4534619b0e1641641","patch":"@@ -1,117 +0,0 @@\n-# Creating accessible PowerPoint documents\n-\n-\n-\n-\n-## Introduction\n-\n-To produce accessible PowerPoint documents, one has to follow recommendations. Fortunately, PowerPoint comes equipped with a tool to check accessibility.\n-It pinpoints the main issues and suggests solutions to remedy them.\n-\n-This being said, even after correcting said issues, we realised that some elements (SmartArt, tables, …) were not always correctly vocalised by screen readers.\n-This is why, when your presentation is done, we recommend to export it in PDF before broadcasting the document: the Export option in PowerPoint gives better results with assistive technologies; also it removes animations, which are often a problem for people with vision problems.\n-\n-## Recommendations\n-\n-Below you will find a summary of recommendations that provide better accessibility with PowerPoint.\n-For more information, please refer to the guides provided on the DINSIC website (in French).\n-\n-Our tests were done using Office 2010 with Jaws 17 and NVDA 2017-1. The below recommendations are the result of these tests.\n-\n-### 1. Use slide masks\n-\n-Presentations must be created using slide masks (menu: Display > Slide masks). Then use checkboxes “Title”, “Footers”, and the menu “Insert reserved space”.\n-\n-### 2. Check the reading order of elements\n-\n-The reading order must be checked through the Selection pane (menu Home > Organise > Selection pane). Be careful: the last element in the list is the first read by screen readers: the reading order must thus be from bottom to top in your slide masks.\n-\n-### 3. Give a unique title to each slide\n-\n-Each slide must have a unique title. This must be added in the zone titled “Click to add a title”.\n-\n-### 4. Provide replacement text for images\n-\n-If the image conveys information, you must provide a replacement text describing its content (right click, Image format > Replacement text > Description field).\n-If the image is strictly for decoration, the Description field must be left empty.\n-\n-\n-### 5. Make simple tables\n-\n-Data tables must stay simple. Avoid blending cells together. Avoid inserting images: they will not be read as table elements but as independent elements which will be read before or after the table according to the internal document’s reading order. Leave no empty cell.\n-\n-### 6. Use SmartArt rather than assembling text and shapes\n-\n-SmartArt enables you to integrate images and text that will be vocalised in the proper order. All SmartArt clips are not correct yet, be careful.\n-\n-### 7. Add a replacement text to graphics\n-\n-The content of graphics must be described in the Replacement text for the graphic (Object format > Replacement text > Description).\n-\n-### 8. Ensure colour is not the only means to convey information\n-\n-Information given through colour must also be conveyed via another means like shape, position, size…\n-\n-### 9. Ensure a sufficient contrast\n-\n-Contrast between the colour of text and of its background must be sufficient:\n-- 4.5:1 for normal-size text;\n-- 3:1 for bigger text.\n-\n-Contrast can be verified with the Colour Contrast Analyzer.\n-\n-### 10. Define language\n-\n-Language must be defined through the menu: File > Options > Language.\n-Words or grops of words in another language must be explicitly described as such (menu: Revision > Language > Define the verification language).\n-\n-### 11. Use the automated Accessibility checker\n-\n-PowerPoint provides an Accessibility checker (menu File > Check for problems > Check accessibility). It lists all contents prone to be hard to deal with.\n-\n-### 12. Exporting the presentation to PDF\n-\n-To export to PDF you only need to go to File > Save as. Choose a name and select PDF as file type.\n-The first time, make sure that the “Accessibility-friendly document structure tags” checkbox in Export options is checked.\n-\n-## External resources\n-\n-- Creating accessible office documents (in French), DINSIC.\n-- PowerPoint accessibility, WebAIM.\n-\n-## Results of our tests\n-\n-We tested the behaviour of NVDA (version 2017.1) and Jaws (version 17) under Windows with a PDF file generated with PowerPoint 2010.\n-\n-### Tables\n-\n-Tables were vocalised correctly with Jaws and NVDA.\n-\n-### Tables with replacement text\n-\n-NVDA: tables were still vocalised, replacement texts were ignored.\n-Jaws: tables were not vocalised any more, replacement texts were ignored.\n-\n-\n-### SmartArt\n-\n-Same behaviour for Jaws and NVDA: SmartArt texts were vocalised (not always in the proper order though).\n-\n-### SmartArt with replacement texts\n-\n-NVDA: expected behaviour, replacement texts were read instead of the SmartArt.\n-Jaws: SmartArt were not vocalised any more, replacement texts were ignored.\n-\n-### Graphics\n-\n-Jaws and NVDA had the same behaviour: figures in graphics were vocalised.\n-\n-### Graphics with replacement texts\n-\n-Jaws and NVDA behaved as expected: replacement texts were vocalised instead of the graphics.\n-\n-\n\\ No newline at end of file"},{"sha":"93dd408b4dd17ca51d9c78c7d73940ff4685f2e8","filename":"others_EN/output/markdown/word.md","status":"removed","additions":0,"deletions":111,"changes":111,"blob_url":"https://github.com/Orange-OpenSource/a11y-guidelines/blob/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Fword.md","raw_url":"https://github.com/Orange-OpenSource/a11y-guidelines/raw/969860377f2a87882b0ac0b4534619b0e1641641/others_EN%2Foutput%2Fmarkdown%2Fword.md","contents_url":"https://api.github.com/repos/Orange-OpenSource/a11y-guidelines/contents/others_EN%2Foutput%2Fmarkdown%2Fword.md?ref=969860377f2a87882b0ac0b4534619b0e1641641","patch":"@@ -1,111 +0,0 @@\n-# Creating accessible Word documents\n-\n-\n-\n-\n-## Introduction\n-\n-Accessible Word documents are needed in order to be read by all users. Creating accessible Word documents requires to respect the following recommendations. It also enables you to produce accessible PDF documents through the PDF export functionality inside Word.\n-\n-## Recommendations\n-\n-\n-You will find below a summary of the recommendations to follow. For more detail, please refer to the DINSIC website (in French).\n-\n-### 1. Use “Heading” styles for headings and sub-headings\n-\n-Headings and sub-headings must use the “Headings” styles (Heading 1, Heading 2, etc.) to structure the document’s content and provide easy access to them.\n-\n-### 2. Use the “Normal” style for texts\n-\n-The “Normal” style must be used for all text paragraphs (default style).\n-\n-### 3. Use dedicated styles to emphasize some contents.\n-\n-Use predefined styles to emphasize some contents (e.g. quotes, legends, etc.) rather than using character formatting tools (bold etc.).\n-\n-### 4. Don’t insert empty lines\n-\n-Space between lines must be created through Paragraph options, where you can define the space before and after a paragraph.\n-\n-Page jumps must be created via proper “Jumps” (Insert > Page jump, new page).\n-\n-### 5. Use bulleted lists\n-\n-Lists must be made using the option “Bulleted list” or “Numbered list”, and not by inserting dashes into the text.\n-\n-### 6. Use footnotes\n-\n-Options to insert “Footnotes” and “Endnotes” must be used to properly insert notes in your document.\n-\n-### 7. Number your pages\n-\n-The “Page number” option makes it easier to get one’s bearings in a document.\n-\n-### 8. Use “Columns” to layout text\n-\n-The “Columns” option in the Layout group must be used (instead of tables) to layout the page as proper columns.\n-\n-### 9. Define the anchor for objects inserted into the page\n-\n-When you insert objects (image, shape, SmartArt, etc.), it is necessary to define an anchor point: in the options for page flow, choose the option “Aligned on the text” or “Top and bottom”.\n-\n-### 10. Avoid text zones\n-\n-Floating text zones are not always properly read by screen readers. Texts can be emphasized through the use of borders around a paragraph, for instance.\n-\n-### 11. Ensure colour is not the only means to convey information\n-\n-Information given through colour must also be conveyed via another means like shape, position, size…\n-\n-\n-### 12. Ensure a sufficient contrast\n-\n-Contrast between the colour of text and of its background must be sufficient:\n-- 4.5:1 for normal-size text;\n-- 3:1 for bigger text.\n-\n-Contrast can be verified with the Colour Contrast Analyzer.\n-\n-### 13. Define language\n-\n-Language must be defined through the menu: File > Options > Language.\n-Words or groups of words in another language must be explicitly described as such (menu: Revision > Language > Define the verification language).\n-\n-### 14. Provide replacement text for images\n-\n-If the image conveys information, you must provide a replacement text describing its content (right click, Image format > Replacement text > Description field).\n-If the image is strictly for decoration, the Description field must be left empty.\n-\n-### 15. Make simple tables\n-\n-Data tables must stay simple. Avoid blending cells together. Avoid inserting images: they will not be read as table elements but as independent elements which will be read before or after the table according to the internal document’s reading order. Leave no empty cell.\n-\n-### 16. Use the automated Accessibility checker\n-\n-Word provides an Accessibility checker (menu File > Check for problems > Check accessibility). It lists all contents prone to be hard to deal with and automatically detects failures. This tool must be used as it provides a huge help; however it does not prevent you from checking and applying all the recommendations provided in this page.\n-\n-### 17. Exporting the document to PDF\n-\n-To export to PDF you only need to go to File > Save as. Choose a name and select PDF as file type.\n-The first time, make sure that the “Accessibility-friendly document structure tags” checkbox in Export options is checked.\n-\n-Please note that in Word for Office 2010 generated PDF documents can show accessibility issues, e.g. for the vocalisation of images. These issues were corrected in the following versions of Microsoft Office.\n-\n-### 18. Insert an table of contents\n-\n-For any long document (more than 2 pages), insert an automatically generated table of contents, in the menu & nbsp ;: References & nbsp;> Table of contents.\n-It makes easier for everyone to find their way around and quickly go to the content you want to read.\n-\n-Note that you must update this table of contents as soon as you change the structure of the content, so prefer to generate the table of contents at the end of the content modifications.\n-\n-## External resources\n-\n-- Creating accessible office documents (in French), DINSIC.\n-- Word Accessibility, WebAIM.\n-\n-\n\\ No newline at end of file"}]}