Authoring Tool and Syllabus - PDF accessibility validation

ecureuill commented 4 years ago

For PDF component in Authoring Tool and for Syllabus (pdf option) add the accessibility settings

Text Alternatives

[x] Add Tab: Text Alternatives

Add inputs in correspondent panel:

[x] hasImage: System should provide radiobuttons (yes/no) asking if the pdf contains images
[x] hasAlt: If hasImage === true, System should provide radiobuttons (yes/no) asking if All images has text alternatives or is marked as decorative
[x] If hasImage === false, System should count this accessibility resource as "well configured"
[x] If hasAlt === true, System should count this accessibility resource as "well configured" (#167)
[x] If hasImage === true && hasAlt === false, System should count this accessibility resource as "misconfigured"
[x] #46 More details: Add examples on how to check add alt text for images in PDF, MS Word, Open Office

Navigation

[x] Add Tab: Navigation

Add inputs in correspondent panel:

[x] hasBookmarks: System should provide radiobuttons (yes/no) asking if the pdf contains a Table of Contents displayed in the side panel (not in the documents pages)
[x] isBookmarksCorrect: If hasBookmarks === true, System should provide radiobuttons (yes/no) asking if is bookmarks linking to correct sections in the document
[x] If hasBookmarks === false, System should count this accessibility resource as "well configured"
[x] If hasBookmarks === true && isBookmarksCorrect === true, System should count this accessibility resource as "well configured" (#114)
[x] If hasBookmarks === true && isBookmarksCorrect === false, System should count this accessibility resource as "misconfigured"

[x] screenReader: System should provide radiobuttons (yes/no) asking if the pdf contents are read aloud in the correct order when using a Screen Reader
[x] If screenReader === true, System should count this accessibility resource as "well configured" (#77 #112)
[x] If screenReader === false, System should count this accessibility resource as "misconfigured"
[x] focusOrder: System should provide radiobuttons (yes/no) asking if the pdf contents are focused in the correct order when using tab key
[x] If focusOrder === true, System should count this accessibility resource as "well configured" (#112 #101 #77)
[x] If focusOrder === false, System should count this accessibility resource as "misconfigured"

Structures

[x] Add Tab: Structure

Title:

[x] hasTitle: System should provide radiobuttons (yes/no) asking if * document has a title and it is correctly marked up as Title element**
[x] If hasTitle === true, System should count this accessibility resource as "well configured" (#53 )
[x] If hasTitle === false, System should count this accessibility resource as "misconfigured" Numbering:
[x] hasNumbering: System should provide radiobuttons (yes/no) asking if the pdf document has numbering, the numbering is consistent (same format) and iscorrecty read aloud by screen reader
[x] If hasNumbering === true, System should count this accessibility resource as "well configured" (#76 #117 #128 )
[x] If hasNumbering === false, System should count this accessibility resource as "misconfigured" Language:
[x] hasLanguage: System should provide radiobuttons (yes/no) asking if the pdf document was configured with the correct language
[x] If hasLanguage === true, System should count this accessibility resource as "well configured" (#120 )
[x] If hasLanguage === false, System should count this accessibility resource as "misconfigured"

Language of Part:

[x] hasLanguagePart: System should provide radiobuttons (yes/no) asking if the all passage, phrase, or word that differs from the default language of the document is marked up with the correct language
[x] If hasLanguage === true, System should count this accessibility resource as "well configured" (#121)
[x] If hasLanguage === false, System should count this accessibility resource as "misconfigured"

Form
[x] Add Tab: Structure Required fields:
[x] hasForm: System should provide radiobuttons (yes/no) asking if the pdf document has form
[x] hasRequiredFields: If hasForm === true, System should provide radiobuttons (yes/no) asking if the pdf has required fields
[x] isRequiredFields: If hasRequiredFields === true, System should provide radiobuttons (yes/no) asking if all required fields are configured as required
[x] If isRequiredFields === true, System should count this accessibility resource as "well configured" (#132 )
[x] If isRequiredFields === false, System should count this accessibility resource as "misconfigured"
[x] hasLabels: If hasForm === true, System should provide radiobuttons (yes/no) asking if all fields has visible label and are read aloud by screen reader
[x] If hasLabels === true, System should count this accessibility resource as "well configured" (#132 #76 #136 )
[x] If hasLabels === false, System should count this accessibility resource as "misconfigured"

Text Content

[x] Add Tab: Text Content

Data Tables:

[x] isTable: System should provide radiobuttons (yes/no) asking if all tables are marked up as Table element and read aloud by a screen reader in a way that preserved logical relationships among tablem header and data cell
[x] If isTable === true, System should count this accessibility resource as "well configured" (#76)
[x] If isTable === false, System should count this accessibility resource as "misconfigured"

List:

[x] isList: System should provide radiobuttons (yes/no) asking if all lists in document is correctly marked up as List element
[x] If isList === true, System should count this accessibility resource as "well configured" (#76 )
[x] If isList === false, System should count this accessibility resource as "misconfigured"
Text Content

Abbreviation:

[x] isAbbreviation: System should provide radiobuttons (yes/no) asking if "all abbreviation has an expansion configured".
[x] If isAbbreviation === true, System should count this accessibility resource as "well configured" (#123)
[x] If isAbbreviation === false, System should count this accessibility resource as "misconfigured"

Headings:

[x] isHeadings: System should provide radiobuttons (yes/no) asking if all headings are marked up as heading element, not only styled
[x] If isHeadings === true, System should count this accessibility resource as "well configured" (#76 #63 #118 #110 )
[x] If isHeadings === false, System should count this accessibility resource as "misconfigured"

Links:

[x] isLink: System should provide radiobuttons (yes/no) asking if all links are marked up as link element, not only styled, and has text description
[x] If isLink === true, System should count this accessibility resource as "well configured" (#76 #101 #113 )
[x] If isLink === false, System should count this accessibility resource as "misconfigured"

CAndresH commented 3 years ago

Camila I have a question: Where on the platform should these radio buttons go?

in the part of configure accessibility?, after upload an image?, after uploading the pdf should appear this menu with the option configure accessibility and configure accessibility later, right?

the same for the other options: Navigation,text content, form and structures, should they go the same way in a menu like this?

CAndresH commented 3 years ago

Another question is how do these new accessibility parameters affect the reports?

for example now we have parameters like hasTitle, hasNumbering, hasLanguage, screenReader and others, and I don't know what type of disability they configure for example: screenReader configures visual impairment?

CAndresH commented 3 years ago

This type of accessibility should be created only for the part of the syllable or when a teacher uploads a pdf in a course as well?

ecureuill commented 3 years ago

Hi @CAndresH ! Exactly, this radios will be part of the Accessibilty Configuration after teacher upload an PDF on Program step and also after upload syllabus. And each item that is a Tab in this issue, should be a tab/navigation in the Accessibility Configuration form.

About the report. For each accessibility option, check for the "well configured" rule, they have an related issue If you open the related issue, you can check the labels (yellow labels started with "a11y") to check which disabilities it affects In above example, thus, if teacher selected to make the course accessible to cognitive or visual then this item should be calculated in the report

github-actions[bot] commented 3 years ago

This feature have been implemented and is ready for Funcional Test. Please, test the feature.

github-actions[bot] commented 3 years ago

Functional Test failed! Please, review your solution.

task "#46 More details: Add examples on how to check add alt text for images in PDF, MS Word, Open Office" from requirement has not been done

CAndresH commented 3 years ago

Hello @rebeccamello @caroltaus, @MAmelia , I understand this must go under the option to upload the pdf ?, but I can not do this requirement if you do not upload the information that should go in this part, remember that Maria Amelia in the meetings some time ago said that she was going to upload the information that we must place in the "More datails" and "Help me decide" options, but we still don't have that information

caroltaus commented 3 years ago

can you please provide this information? @flaviolima thank you!

github-actions[bot] commented 3 years ago

This feature have been implemented and is ready for Funcional Test. Please, test the feature.

github-actions[bot] commented 3 years ago

Functional Test failed! Please, review your solution.

More details button in accessibility with text alternatives with "Add examples on how to check add alt text for images in PDF, MS Word, Open Office" information is still missing. Please wait for @flaviolima to provide this information.

CAndresH commented 3 years ago

@rebeccamello @caroltaus @flaviolima, Hello team, where is the information that should be placed in this part?,

flaviolima commented 3 years ago

Hi @CAndresH I'm providing this information and will be available in the next days. Thanks.

caroltaus commented 3 years ago

Info was provided by @flaviolima at https://github.com/solex2006/SELIProject/issues/46

github-actions[bot] commented 3 years ago

This feature have been implemented and is ready for Funcional Test. Please, test the feature.

github-actions[bot] commented 3 years ago

Functional Test passed! Please, make a PULL REQUEST or, if already merged, close the issue.

solex2006 / SELIProject