W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2018

Re: Bold vs Strong

From: Vinil Peter <vinilpeter.wcag@gmail.com>
Date: Mon, 06 Aug 2018 01:47:43 +0530
To: Katie Haritos-Shea <ryladog@gmail.com>
CC: WAI Interest Group <w3c-wai-ig@w3.org>
Message-ID: <7b131f98-7ebb-410e-816c-7486c23d0335@gmail.com>
Hi Katie,

Thanks for the information and guidance.

Vinil Peter, PMP​

On Aug 5, 2018, 11:09 PM, at 11:09 PM, Katie Haritos-Shea <ryladog@gmail.com> wrote:
>Please see WCAG 2 failure technique as rationale for using semantic
>F2: Failure of Success Criterion 1.3.1 due to using changes in text
>presentation to convey information without using the appropriate markup
>On Sun, Aug 5, 2018, 11:17 AM Vinil Peter <vinilpeter.wcag@gmail.com>
>> Dear colleagues,
>> I have been asked to provide my thoughts on a debate on the use of
>> <b> and strong <strong> for one of my clients. The client's internal
>> accessibility testing team marked all the instances where <b> was
>used as
>> errors and recommended to change them to <strong> so that screen
>> read out the text with added emphasis. This has brought their quality
>> compliance scores down drastically. The client's developers are
>> about this and claim that they should not be marked down as there is
>> clear guideline or fine print that mandates use of <strong> over <b>.
>> Moreover, W3C has not deprecated <b> yet and it's usage is still
>> <b> has been in use since ages and asking to replace all bold text
>> strong is like declaring that  use of <b> should be banned
>> I am planning to give my recommendation to use <strong> in headers or
>> functionality names etc. if the text is bold as per  design, while it
>> still fair to allow use of <b> for other bold text. The 'appropriate
>> of bold or strong is finally the designer's call as there is no clear
>> guideline.
>> Is my recommendation correct or am I missing something? What your
>> and have you come across any such debate?
>> Regards,
>> Vinil Peter, PMP
Received on Sunday, 5 August 2018 20:18:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:37:20 UTC