WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: A question about content editable attribute with screen readers in HTML

for

From:
Date: Jan 30, 2019 6:48AM


Thank you so much for your email.
I tested with NVDA and JAWS with Chrome and Firefox with latest screen reader version.
And I know that general content editable is read by screen readers.
For example, in my wordpress hompage with Gutenberg, there is no problem to read.
But in our Korean homepage smart editor with block navigation, even if there are many lines, screen readers say just blank.
I really want to share the code, but I have no code, because I’m a accessibility tester.
Also I saved the editor in my local PC, but the behavior is different.
Of course if you cannot the original page, you might give me hard to advice, but if you have a guess and clue how to solve, please let me know.

Thank you.

김형섭 / Hyongsop Kim
(주)엔비전스 / 웹접근성사업팀 팀장

서울시 종로구 가회동 1-29
1-29 Gahoe-dong, Jongno-gu, Seoul, Korea
T. +82 2 313 9977 F. +82 2 313 3645 M. +82 10 3316 5996

http://dialogueinthedark.co.kr
http://cafe.naver.com/dialogueinthedark


-----Original Message-----
From: "Léonie Watson"< <EMAIL REMOVED> >
To: "WebAIM Discussion List"< <EMAIL REMOVED> >; "김형섭"< <EMAIL REMOVED> >;
Cc:
Sent: 2019-01-30 (수) 22:36:16
Subject: Re: [WebAIM] A question about content editable attribute with screen readers in HTML

Hello Hyongsop Kim.

Can you share an example of your code?

Screen readers should be able to read the contents of an element with
contenteditable, but it will depend on which screen reader and browser
you are using. Which screen readers and browsers are you testing with?

Léonie.



On 30/01/2019 13:20, 김형섭 wrote:
> Hello, I’m Hyongsop Kim in Korea and accessibility tester.
> May I ask your help regarding smart editable content with accessibility issue?
> In Korea one company developed smart editor based on block navigation with contenteditable attribute.
> By the way, even if I type several lines within edit area, screen readers doesn’t detect any text.
> So in order to report this issue, I looked into Google Docs.
> Because if I give similar cases, I think they will get clue more easily.
> Of course Google Docs is not based on block navigation.
> But if screen reader support is disabled, it also doesn’t support screen reader that enable reads the text inside of editable area.
> So I supposed that if I find the difference markup with HTML OR JS between screen reader support is enabled or not, it will have a clue to report to our developers to solve this problem.
> But because Google docs source code is too complicated, I can’t find how difference between screen reader support is enabled and not.
> So below is my question.
> If screen readers, like NVDA, can’t read the contents of editable area, how to fix the problem that let screen readers enables the text?
> In Google Docs, why screen readers can’t detect text while screen reader support is disabled?
> If you share the knowledge, it will be a lot of helpful to improve our Korean smart editor accessibility issues.
>
> Thank you.
> > > > >

--
@LeonieWatson tink.uk Carpe diem