Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certfied or Evaluated? #473

Open
gautierchomel opened this issue Nov 13, 2024 · 6 comments
Open

Certfied or Evaluated? #473

gautierchomel opened this issue Nov 13, 2024 · 6 comments
Labels
a11y-display-guide Issue with the UX Guide principles or techniques

Comments

@gautierchomel
Copy link
Collaborator

gautierchomel commented Nov 13, 2024

While trying to explain the difficulties of translating “Certified” into French (#472), I realized that EPUB Accessibility 1.1 section 3.5 Conformance reporting uses the wording “Evaluator” and “Evaluated.”

I suggest that we adopt this wording for the Display guide instead of “Certified By” and “Certified”.

I think it best reflects the reality, especifically in the case of Self evaluation.

It also allows for better visibility of third party certifications, which includes more than just an evaluation.

@gautierchomel gautierchomel added the a11y-display-guide Issue with the UX Guide principles or techniques label Nov 13, 2024
@GeorgeKerscher
Copy link
Collaborator

Do we need these words added to the terms section?

@mattgarrish
Copy link
Member

mattgarrish commented Nov 15, 2024

I recall we had this problem of certification vs. evaluation when we went through the ISO process. They also view certification in legal terms, so the language of certification was changed to evaluation. It was too late to change the property names, but if you compare the IDPF 1.0 version to the 1.1 version there's now a distinct lack of use of certify beyond those names.

@GeorgeKerscher
Copy link
Collaborator

I thought I would add this post from a NISO discussion list in the library space:
**
I think there's a critical issue to discuss, along with the risk it poses.
• The critical issue is recognizing a conflict of interest in self-declarations of accessibility.
• The risk is a breach of trust with library users who depend on accessibility metadata.
We would recognize the conflict of interest in a restaurant self-declaring its kitchen met health standards. That's why there are restaurant inspectors. Likewise, there's also a conflict of interest in publishers or libraries self-declaring their content was built or remediated to accessibility standards.

What's the risk? Outrage from users, betrayal of trust, and harm to users.

In the context of websites, there has been tremendous vocal outrage within blind communities about companies that make false statements about creating accessible websites. In 2021, the US National Federation of the Blind (NFB) issued a resolution Regarding the Use of Overlays to Make Websites Accessible to the Blind.

In this 2021 personal appeal on YouTube (3.5 minutes), Haben Girma, who is a Harvard law graduate and is Deafblind, expresses deep frustration about companies claiming they can easily make websites accessible. She emphatically expresses how trust has been broken.

Two years later, the founder of one of the companies issued an apology to the NFB. At the 2023 convention, the founder also addressed NFB members about how the company was trying to rebuild trust.

In the context of libraries and books, I asked a blind researcher to join a discussion with sighted librarians about accessible discovery experiences. On the issue of books being described as accessible when they weren't, the researcher said it was like being gaslighted.

What's a solution for this IFLA Network? A solution might include recognizing the need for independent 3rd parties to certify claims related to accessible metadata. In the context of publishing, we find an example in Benetech, which certifies the workflow of publishers wanting to create accessible books. Also, encouraging publishers and libraries to engage and work with people with disabilities, including in co-designing enjoyable reading experiences, could help.

@gautierchomel
Copy link
Collaborator Author

Could we imagine using "Evaluated" when there is no certifier credential and "{certifier credential} certified " when there is a certifier credential?

@clapierre
Copy link
Collaborator

clapierre commented Dec 5, 2024

The editors met and we decided to handle this by creating two sets of strings one for a stricter "Certification" vs. an "Evaluation"

We will also add notes to the main guidelines document and both techniques documents and comments in the JSON file stating that it will be up to the implementor to decide if certification vs. evaluation is warranted for their country's interpretation of these terms.

conformance-certifier = "certifier"
conformance-certifier-credentials = " with a credential of "
conformance-certification-info = "The publication was certified "
conformance-certifier-report = "For more information refer to the certifier's report"

and

conformance-evaluator = "evaluator"
conformance-evaluator-credentials = " with a reference of "
conformance-evaluation-info = "The publication was evaluated "
conformance-evaluation-report = "For more information refer to the evaluator's report"

Not really sure if we need the two prefix's unless we change the ID's from
conformance-certifier-credentials-prefix = " by"
conformance-certification-date-prefix = " on "
conformance-evaluator-credentials-prefix = " by"
conformance-evaluation-date-prefix = "on"
to
conformance-credentials-prefix = " by "
conformance-date-prefix = "on "

@GeorgeKerscher
Copy link
Collaborator

I believe we are getting away from requiring a prefix and constructing a sentence. Instead we are making each statement a stand alone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y-display-guide Issue with the UX Guide principles or techniques
Projects
None yet
Development

No branches or pull requests

4 participants