almanac | Tools for working with recurrence rules, holidays, and calendars | Calendar library

Now, how do screen readers handle the content in these ::before and ::after elements?

It depends on the screen reader, browser and OS combination used. Sometimes it is rendered, sometimes it isn't.

As far as I remember, Jaws+IE and Jaws+firefox don't render it, nor NVDA+IE, but NVDA+firefox does for example.

In consequence, you'd rather don't use ::before and ::after. At least, don't use them to convey important information. Aria-hidden is much more widely and uniformly supported.

ADditionally, both are legitimally acceptable, if we look at it well:

• Outside a few notable exceptions (display:none for example), screen readers shouldn't bother with CSS, since CSS give instructions for presentation only. IN this logic, since it's just presentation, it isn't important, so let's ignore ::before and ::after.
• IN the opposite side, ::before and ::after are text contents to be added to the element. Technically we can create a DOM element for displaying that text (probably that some browsers do it that way). Since it's a DOM element now, there's no reason not to render it.

IN short, that's controvertial. In the same kind of contradiction, we have CSS counters, and quoting via CSS. Are these two only presentation ? probably not entirely. Is text in ::before and ::after only presentation ? IN your case yes, but you can as well add some text being not presentational at all.

In addition to that question, does it make a difference how the styles are loaded? E.g. inline, using a link or with a style tag?

It doesn't change anything as far as I have tested.

(I've read about the CSS speak property, but it doesn't seem to be supported anywhere yet...)

CSS speak won't probably ever supported. That's a 10+ years old project, more or less abandonned nowadays, for quite good reasons.

Things like voice, genre, accentuation, pitch, how to make pauses according to punctuation, sound cues, etc. are private preferences to be configured by the screen reader user. Website designers musn't interfer with that in any way. There exists really no "standard voice" that would be acceptable for most users. Websites aren't audio books. Audio books are cool, but they don't serve the same purposes.

Looks like overflow-wrap provides more opportunities for the text to wrap.

I modified your code to show both cases, one after the other, for easier comparison.

Edit: good catch on the missing { - after fixing that I agree there appears to be no difference.

I'll leave this answer here as it is still a good code sample for testing alternatives.

ANSWER: The pluses are ugly and seem to be a way to save the quotes in the attribute to make the shortest code possible as an inline attribute - Not recommended since it may not work in all browsers.

Details about the code

MDN Box shadow

Box-shadow property adds shadow effects around an element's frame. You can set multiple effects separated by commas. A box shadow is described by X and Y offsets relative to the element, blur and spread radius, and color.

CSS-Tricks box shadow

box-shadow: [horizontal offset] [vertical offset] [blur radius] [optional spread radius] [color];

I think your problem is that the MFRC522 RFID reader is a very basic/old design and really only supports MIFARE type cards (which are the non standardised original card format). While Host Card emulation uses ISO/IEC 14443A (mostly) as a base it uses other higher level protocols to emulate a NFC Type 4 card which is not supported by that card reader.

If you look at an Arduino library for the reader https://github.com/miguelbalboa/rfid#troubleshooting

My mobile phone doesn't recognize the MFRC522 or my MFRC522 can't read data from other MFRC522
Card simulation is not supported.
Communication with mobile phones is not supported.
Peer to peer communication is not supported.

As the library suggest if you want more feature use a PN532 based modules instead.

If you look at an Arduino library for the PN532 https://github.com/Seeed-Studio/PN532#Features

Communicate with android 4.0+(Lists of devices supported)

Change the display from block to inline-block and remove the width:

The problem is you cannot use HCE on Android to emulate a Mifare Classic 1K (https://www.nxp.com/docs/en/data-sheet/MF1S50YYX_V1.pdf) as this is a custom Type NFC card. As HCE is about emulating Type 4 cards. See https://developer.android.com/guide/topics/connectivity/nfc/hce#SupportedProtocols

And the below image helps understand the type.

You can see this from it's datasheet, nowhere does it talk about AID's and standard Type 4 NFC commands

Though Type 2 and Type 4 can share the Anti Collision mechanism and Reading the UID (which is part of the process) any other access methods are not shared.

Type 4 Spec for reference is at http://apps4android.org/nfc-specifications/NFCForum-TS-Type-4-Tag_2.0.pdf

I have seen some USB readers that offer on reader emulation of other card types but not HCE where the host does the emulation not the NFC hardware.

The Authentication on Type 4 Cards or emulated ones is handled differently.

You can emulate a MIFARE DESFire Card as that is a Type 4 card.

The specs of your card reader are not documented well and it looks very "lite" and that it does not support any of the higher level protocols needed to talk to non Mifare Classic cards. It could support them but as Mifare protocol was the original spec, it could be possible for it to be and old design and only support the Mifare protocol.

You can use this css-tricks to change the cursor. I hope this is helpful. https://css-tricks.com/using-css-cursors/

I have tried my best to avoid my feel of possibility of opinion based answers on this question and looked this up on internet. Found out it is quite hard to find any relevant info that I could trust, so I enumerate these posts (except wikipedia):

timeanddate is stating the exact time is 18:20 UTC on December 21, which is as you have calculated

winstars have stated the time when the planets will be at closest angle as 18:25 UTC and they mention that conjunction will occur at 13:30 UTC, I am not sure if that is the first time.

Not sure how relevant is this, but the conjunction here is stated to be 6.2 degreest at 17:32 GMT, thus 18:32 UTC

The most relevant source I was able to find was in the sky, where the time was estimated exactly to 13:24 UTC., based on calculations on data by Jet Propulsion Laboratory - source code can be checked here (c).

You can see that mostly not both types of calculation are used, and that the times vary. The reason of that is that in such calculations you need very long floats for best precision. As you are limited by the machine you use, the precision is not perfect. Such as @bad_coder has suggested, you might get better answer in Astronomy stack exchange.

Although without moving we can't move the table down and wrap the text around it, but there is a magical way through you can do it without moving html's code.

We can achieve your thoughts by inserting a div with an id of hidden as: