manipulating complex objects file has too many `<dfn>`

Describe the Issue

here is the file raw notice there are a lot of definition elements <dfn>, but there is lack of definition.

Edit: the below paragraph is wrong check bbsmooth comment below.

I think this harming accessibility, because in Mozilla docs it says that “indicate the term being defined within the context of a definition phrase or sentence”, but we aren’t defining them.

• manipulating complex objects
• create decimal numbers
• caesars-chiper

Affected Page

https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/basic-javascript/manipulating-complex-objects

Your code

Sometimes you may want to store data in a flexible <dfn>Data Structure</dfn>. A JavaScript object is one way to handle flexible data. They allow for arbitrary combinations of <dfn>strings</dfn>, <dfn>numbers</dfn>, <dfn>booleans</dfn>, <dfn>arrays</dfn>, <dfn>functions</dfn>, and <dfn>objects</dfn>.

Expected behavior

Definition following the elements

Additional context

I maybe overthinking like how I usually does, but I do think it’s best to remove these elements.

[bbsmooth]

The use of<dfn> is required in order to meet level AAA

SC 3.1.3 does not really say this. It says that a “mechanism” should be available for identifying specific definitions of words or phrases used in an unusual or restricted way. This mechanism can be a variety of things and does not require a specific HTML element. If we really wanted to meet SC 3.1.3 then we would have to either define each of these terms in the instructions or provide a link to their definitions. But I’m not sure that they would even fall under SC 3.1.3 in the first place because it applies to words or phrases “used in an unusual or restricted way” and these are all terms commonly used in web development. I’m not saying we shouldn’t perhaps define some of these, just that SC 3.1.3 does not technically apply here.

Regardless, the <dfn> element is intended to be used when the definition is actually being given on the page, which we are not doing here, so technically it is probably not the best element to use. But as far as accessibility is concerned, it is not an issue (as I explained above).

[huyenltnguyen]

I went through the W3C specs and I think we should keep this as-is. The use of<dfn> is required in order to meet level AAA, but:

Certain disabilities make it difficult to understand nonliteral word usage and specialized words or usage. Certain disabilities make it difficult to understand figurative language or specialized usage. Providing such mechanisms is vital for these audiences. Specialized information intended for non-specialist readers is encouraged to satisfy this Success Criterion, even when claiming only Single-A or Double-A conformance.